Graphical user interface for tracking and displaying patient information over the course of care

ABSTRACT

A system for generating an interface that tracks information over the course of patient care is provided. The system includes an interface component configured to generate an interface that facilitates tracking a course of care of a patient, wherein the interface comprises a plurality of input compartments defined by a first axis comprising columns corresponding to sequential points in time over the course of the care and a second axis comprising rows respectively corresponding to patient care events or patient conditions associated with the course of the care. The system further includes a reception component configured to receive input regarding a patient care event or condition that occurred over the course of the care, and a logging component configured to fill one or more input compartments respectively corresponding to a point or period of time associated with occurrence of the patient care event or patient condition.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is continuation of and claims priority to U.S. patentapplication Ser. No. 14/304,593 filed on Jun. 13, 2014, entitled“GRAPHICAL USER INTERFACE FOR TRACKING AND DISPLAYING PATIENTINFORMATION OVER THE COURSE OF CARE.” The entirety of the aforementionedapplication is incorporated by reference herein.

TECHNICAL FIELD

This disclosure relates a graphical user interface for tracking anddisplaying patient information over the course of care.

BACKGROUND

In health care settings, tracking of patients, patient services,medications, and other items or services can provide both betterimmediate management of patient care and better long-term management astracking reports are evaluated to determine where problem areas exist.In healthcare delivery systems, patient flow can be critical, both tothe individual patient and to the overall patient population. Forexample, management of a patient in labor involves various key data anddecision points over the course of labor that guide the physician,midwife or nurse in their scope of clinical decision making. These keydata points are difficult to track for each patient in a clear andconcise fashion over the length of labor. Keeping track of up to themoment data as a clinician moves between multiple laboring patients maybe difficult.

There is a significant opportunity for improvement in tracking patientconditions and health services over the course of patient care. Thevarious transactions involved with a patient admitted to a hospitalrelated to treatment, diagnosis and recovery are currently unmanaged andpoorly integrated and coordinated. The looseness of this process resultsin errors, omissions, missing information, duplication, re-work,inefficiency, sub-optimal quality, poor service, and high cost to thepatient and health care provider.

BRIEF DESCRIPTION OF THE DRAWINGS

This application contains at least one drawing executed in color. Copiesof this patent or patent application publication with color drawing(s)will be provided by the Office upon request and payment of the necessaryfee.

FIG. 1 illustrates a block diagram of an example user interfacefacilitates tracking and displaying patient information over the courseof care in accordance with various aspects and embodiments describedherein;

FIG. 2 presents an example system that facilitates tracking anddisplaying patient information over the course of care in accordancewith various aspects and embodiments described herein;

FIG. 3 illustrates a block diagram of another example user interfacefacilitates tracking and displaying patient information over the courseof care in accordance with various aspects and embodiments describedherein;

FIG. 4 illustrates a block diagram of another example user interfacefacilitates tracking and displaying patient information over the courseof care in accordance with various aspects and embodiments describedherein;

FIG. 5 illustrates a block diagram of another example user interfacefacilitates tracking and displaying patient information over the courseof care in accordance with various aspects and embodiments describedherein;

FIG. 6 illustrates a block diagram of another an example user interfacefacilitates tracking and displaying patient information over the courseof care in accordance with various aspects and embodiments describedherein;

FIG. 7 illustrates a block diagram of another example user interfacefacilitates tracking and displaying patient information over the courseof care in accordance with various aspects and embodiments describedherein;

FIGS. 8A-8B illustrate a block diagram of another example user interfacefacilitates tracking and displaying patient information over the courseof care in accordance with various aspects and embodiments describedherein;

FIG. 9 presents another example system that facilitates tracking anddisplaying patient information over the course of care in accordancewith various aspects and embodiments described herein;

FIG. 10 presents another example system that facilitates tracking anddisplaying patient information over the course of care in accordancewith various aspects and embodiments described herein;

FIG. 11 presents another example system that facilitates tracking anddisplaying patient information over the course of care in accordancewith various aspects and embodiments described herein;

FIG. 12 illustrates a flow chart of an example method for tracking anddisplaying patient information over the course of care in accordancewith various aspects and embodiments described herein;

FIG. 13 illustrates a flow chart of an example method for tracking anddisplaying patient information over the course of care in accordancewith various aspects and embodiments described herein;

FIG. 14 is a schematic block diagram illustrating a suitable operatingenvironment in accordance with various aspects and embodiments.

FIG. 15 is a schematic block diagram of a sample-computing environmentin accordance with various aspects and embodiments.

DETAILED DESCRIPTION

The innovation is described with reference to the drawings, wherein likereference numerals are used to refer to like elements throughout. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofthis innovation. It may be evident, however, that the innovation can bepracticed without these specific details. In other instances, well-knownstructures and components are shown in block diagram form in order tofacilitate describing the innovation.

By way of introduction, the subject matter described in this disclosurerelates to systems and methods that enable health care providers toefficiently and effectively manage care of their patients. In an aspect,a system is provided that includes a patient tracking tool thatfacilitates receiving input regarding patient care events and patientconditions over the course of patient care. The patient tracking toolincludes an interface component configured to generate a graphical userinterface (GUI) that facilitates tracking a course of patient care. Theinterface can include a visualization that resembles a chart having aplurality of input compartments defined by a first axis having columnscorresponding to sequential points in time over the course of the careand a second axis having rows respectively corresponding to patient careevents or patient conditions associated with the course of the care. Thepatient tracking tool further includes a reception component configuredto receive input regarding a patient care event or condition thatoccurred over the course of the care and a logging component configuredto fill one or more input compartments respectively corresponding to apoint or period of time associated with occurrence of the patient careevent or patient condition, in response to reception of the input.

In an aspect, the patient tracking tool can be provided on a device thatis accessible to medical personal involved in the patient care. Thedevice can include a display that presents the interface to the medicalpersonnel and allows the medical personnel to provide the input (e.g.,via touch screen or other input device) regarding occurrence of apatient care event or condition. For example, the patient tracking toolcan be provided on a device located in a patient's hospital room. Thepatient tracking tool can generate a graphical user interface that isdisplayed on the device and charts up to date information regardingconditions of the patient (e.g., heart rate, blood pressure,temperature, etc.) and events (e.g., administration of a drug)associated with care of the patient from the time of admittance to acurrent point in time. Over the course of care, medical personnel caninput the information in real-time for display via the graphical userinterface and/or the information can be received in real time from amedical device (e.g., a heart monitor, pulse oximetry device, etc.). Asa result, the graphical user interface can depict a complete timelinepicture of the various aspects of a course of patient care from the timeof admittance to a current point in time.

In an aspect, at the time a patient is admitted or received, thepatient's medical history and a plan for the patient care is enteredusing the patient tracking tool. The patient tracking tool generates agraphical user interface that includes a date and hours timeline thatrun horizontally (e.g., left to right or an X axis) and a plurality ofdata fields that extend vertically (e.g., from top to bottom or a Yaxis) and below the hours timeline near the left side of the interface.For example, a series of ten to fifteen data fields related to patientconditions and/or patient care events associated with the plan forpatient care can be displayed along a vertical axis tangential from thetimeline. In an aspect, the data fields can be associated with a dropdown input menu that allows a user to select an input option from aplurality of preconfigured input options associated with the data field.

In an aspect, received input data can start a timeline associated with apatient condition or patient care event. Once a timeline is started itwill continue to progress across the interface until new data isreceived indicating a change in the patient condition or patient careevent. In another aspect, received input data can identify a particulartime point that a key event or condition occurred in the course of care.A timeline or key event can be represented by a color bar runninghorizontally right to left across the interface. In an aspects,characteristics associated with a timeline or key event can be includedin the form of text or a symbol located at the tip of the color bar.

In an exemplary embodiment, the subject patient tracking tool canfacilitate tracking patient care during a course of labor. For example,management of a patient in labor may be brief, over a few hours, or maylast several days. Clinicians in most hospital based services arelimited to 8 or 12 hour “on duty” time frames or “shifts.” Accordingly,the care of a mother in labor management often crosses through the careof many clinicians. Depending on the patient care setting, cliniciansinvolved with care can include attending medical doctors (MDs),residents, interns, nurse midwives, registered nurses (RNs), licensedpractical nurses (LPNs), patient care assistants and doulas interactingwith the laboring patient. Clinicians often cover multiple laboringpatients at once and in some cases, information regarding a patient'slabor is communicated to a remote physician to make patient caredecisions based on the communicated information. Therefore, accurate andeffective communication from one clinician to another over the course ofa patient's labor and delivery is paramount to a successful labor anddelivery.

There are key data and decision points in the course of labor that canaffect the outcome of the baby including lifelong cognitive and physicalfunctions. Data points that guide the physician, midwife of nurse intheir scope of clinical decision making are difficult to track for eachpatient in a clear and concise fashion over the length of labor. Keepingtrack of up to the moment data as a clinician moves between multiplelaboring patients may be difficult. The subject patient tracking toolcan provide clinicians with comprehensive picture of the key data anddecision points during the course of labor management.

Various aspects of the subject patient tracking tool are exemplified inassociation with tracking patient care over the course of labor.However, it should be appreciated that the subject patient tracking toolis not limited to tracking patients undergoing labor. The subjectpatient tracking tool can be employed to track patient care events andconditions associated with a patient care scenario that involves caringfor the patient over a period of time. For example, the subject patienttracking tool can be employed to manage patient care with respect totreatment of various diseases over a period of time. In another example,the subject patient tracking tool can be employed to manage course ofcare of patients admitted to the emergency room for various ailments.Still in yet another example, the subject patient tracking tool canassist in managing a course of care for a patient suffering from a heartattack or stroke.

Referring now to the drawings, FIG. 1 depicts an example user interface100 that facilitates tracking patient care events and patient conditionsover the course of labor in accordance with aspects and embodimentsdescribed herein. Aspects of the interfaces, apparatuses, systems orprocesses described in this disclosure can constitute machine-executablecomponents or modules embodied within machine(s), e.g., embodied in oneor more computer readable mediums (or media) associated with one or moremachines. Such components or modules, when executed by the one or moremachines, e.g., computer(s), computing device(s), virtual machine(s),etc. can cause the machine(s) to perform the operations described.

Interface 100 organizes and presents information associated with care ofa patient over the course of labor as a function of time. In particular,interface 100 graphically depicts various patient care events andconditions that occurred over the course of labor up until a time of 24hours after admittance of the patient. Interface 100 includes aplurality of input compartments or cells defined by a first axis 102 anda second axis 130. The first axis 102 corresponds to a timeline andincludes a plurality of columns respectively associated with sequentialpoints in time, beginning with a time at which the patient was admitted.For example, the first axis 102 includes a plurality of columnsrespectively associated with four hour increments of time followingadmittance of the patient. The second axis 130 includes a plurality ofrows respectively associated with a data input fields corresponding topatient care events or conditions. In particular, the second axis 130includes a plurality of rows that correspond to various patient careevents and conditions associated with labor, including admittance 104,rupture of membranes (ROM) 106, provision of cytotec 108, provision ofpitocin 110, stages of labor 112 (e.g., associated with the motherand/or the infant), categories of labor 114 (e.g., associated with themother and/or the infant), dilation 116, blood pressure (BP) 118,magnesium (Mag) or maternal hypertension 120, fetal heart rate (HR) 122,maternal temperature 124, deceleration of fetal HR 126, and accelerationof fetal HR 128.

It should be appreciated that the data fields corresponding to therespective rows of interface 100 are not limited to those describedabove. In particular, a data field in interface 100 can be adapted tocorrespond to any possible patient care event or condition associatedwith a course of labor. For example, one or more of the data fieldslisted above and depicted in interface 100 can be removed and/oradditional data fields can be added. For instance, row 120 correspondingto Mag monitoring could be removed and a new row could be addedcorresponding to fetal station that facilitates tracking informationregarding fetal station. In an aspect, interface 100 can be divided intotwo sections, one having data input rows corresponding to patient careevents and conditions associated with the mother and anothercorresponding to patient care events and conditions associated with theinfant.

Interface 100 graphically depicts various patient care events andconditions that occurred over the course of labor up until a time of 24hours after admittance of the patient. Information or data includedwithin respective input compartments or cells of interface 100 can bereceived and entered over the course of care at the time at which apatient event or condition represented by the data occurs. For example,a user can select a cell (e.g., cell 156) corresponding to a time orhour increment (e.g., 12 hours) and data input field (e.g., dilation116) and enter information for display in the cell indicating occurrenceand/or a characteristic of the patient care event or conditionrepresented by the data field at the time or hour increment (e.g., 4centimeters (cm) for 8 hours (hr)).

In an aspect, information or data included within respective inputcompartments of interface 100 is entered by a medical caregiver. Forexample, using a data interfacing tool (e.g., soft keys, touch screen,voice detection, etc.), a user can select an input compartment definedby a row and a column and enter information representative of thepatient care event or condition associated with the row at a timerepresented by the column. The entered information can include a fillcolor and/or text indicating occurrence of the patient care event orcondition and/or identifying a characteristic of the patient care eventor condition. In another aspect, information or data included withinrespective input compartments of interface 100 is entered automaticallyin response to receipt of the information from a medical device (e.g., aheart rate monitor, a temperature monitor, etc.).

Interface 100 can receive and display various types of data input toindicate occurrence and/or a characteristic of the patient care event orcondition. For example, interface 100 can receive and display textcharacters, symbols and/or colors in various input compartments/cells tomark occurrence or a characteristic associated with a patient care eventor patient condition. In an aspect, input compartments associated withvarious patient events or conditions are filled with a color to indicateoccurrence and/or a characteristic of the patient care event orcondition at a time associated with the input compartment. Differentcolors can be used to distinguish between different patient care eventsor conditions and/or characteristics of the patient care events orconditions. For example, in interface 100, each cell corresponding to anamount of time passed following admittance of the patient is filled withblue, each cell corresponding to an amount of time passed following ROMis filled with green, each cell corresponding to an amount of timepassed following administration of cytotec is filled with yellow, etc.

In an aspect, different colors or color shades can be employed toindicate a characteristic of the information represented thereby. Forexample, different shades of yellow can be employed to distinguishbetween different degrees of dilation. As seen in interface 100, asdilation increase from 2 cm to 9 cm, the shade of yellow associated witheach cell including the dilation information intensifies. A change incolor from bright yellow to lime green in cell 148 can be used toindicate dilation is complete. In another example, different inputcolors can be employed to distinguish between different stagesassociated with labor (e.g., stage I is marked by light green, stage IImarked by light purple) and different categories associated with labor(e.g., category I is marked by pink and category II is marked by red).

Input can be provided within a single cell, (or portion of a singlecell), to mark a fixed event or condition or a characteristic associatedwith on ongoing event or condition at a specific point or period oftime. For example, cell 156 includes color data and text dataidentifying a degree of dilation at time 12 hours. In another example,cell 154 includes color data and text data identifying an amount of time(e.g., 30 seconds) associated with heart rate acceleration between 8 and12 hours following patient admittance. In yet another example, cell 158includes text data identifying a maternal heart rate at 4 hours afteradmittance.

Where a patient care event or patient condition is ongoing, sequentialcells or compartments of a row corresponding to the patient care eventand the times during which the patient care event or condition occurs,are filled with a same solid or color, resulting in the creation of ahorizontal color bar. These color bars can establish a visual timelinefor the duration of a particular patient care event or condition. Forexample, color bar 132 corresponds to an amount of time elapsedfollowing admittance of the patient, color bar 134 corresponds to anamount of time elapsed following ROM, color bar 136 corresponds to anamount of time elapsed following administration of cytotec, color bar138 corresponds to an amount of time elapsed following administration ofpitocin, color bar 140 corresponds to an amount of time elapsed whilethe patient was in stage I of labor, color bar 142 corresponds to anamount of time elapsed while the patient was in stage II of labor, colorbar 144 corresponds to an amount of time elapsed while the patient wasin category I of labor, color bar 146 corresponds to an amount of timeelapsed while the patient was in category II of labor, color bar 150correspond to an amount of time where the maternal blood pressure washigh (e.g., above 145/90), and color bar 152 corresponds to an amount oftime elapsed following administration of magnesium.

In an aspect, data fields or rows associated with ongoing patientconditions/events are configured to automatically populate cellsassociated therewith as time progresses. In particular, after data isreceived at a time indicating onset or occurrence of a patient careevent or condition, cells associated with the patient care event orcondition following the time the data is initially received canautomatically be filled (with a same color) to indicate an amount oftime elapsed following onset of the patient care event or patientcondition and/or an amount of time during which the patient event orcondition persists. For example, when a patient is admitted, a user canmark or fill the initial cell at time 0 hours and field admittance 104(or otherwise provide input data indicating when the patient wasadmitted for association/display in admittance field 104). Respectivecells associated with the admittance field/row 104 can then autopopulate as time progresses with data (e.g., the color blue) until datais received indicating the patient has been released. According to thisaspect, a clock can be employed to detect passage of time in associationwith auto filling of cells.

In addition, key information associated with a color bar can bedisplayed in text at the tip of the color bar. As seen in interface 100,color bar 132 includes text at the tip thereof indicating the patienthas been admitted for 24 hours, color bar 134 includes text at the tipthereof indicating it has been 16 since ROM, color bar 136 includes textat the tip thereof indicating cytotec has been applied 8 hours ago, etc.In an aspect, the information included within a color bar candynamically update to reflect progression of the color bar over time.For example, information identifying an amount of time represented bythe color bar can be included at the tip of the color bar and beautomatically updated or calculated based on a current point in time.

In another aspect, data fields associated with ongoing patientconditions/events are configured to automatically populate cellsassociated therewith as time progresses until new input indicating achange in the patient condition/event is received. For example, when apatient enters stage I of labor, a user can mark or fill the initialcell at time 0 hours and data field/row stage 112 (or otherwise provideinput data indicating when the patient entered stage I of labor forassociation/display in stage field 112). Respective cells associatedwith data field/row stage 112 can then auto populate as time progresseswith data (e.g., the color light green) until new data is receivedindicating the patient is no longer in stage I of labor. For example,regarding generation of interface 100, after the passage of 20 hourstime, new data can be received indicating the patient has entered stageII of labor. At this point, the color bar 140 associated with stage I oflabor is fixed and a new color bar 142 associated with stage II of laboris initiated.

The various data fields 104-128 of interface 100 can be pre-defined ordefined based on user input. For example, a graphical user interface(e.g., interface 100) that facilitates tracking a patient undergoinglabor can include a plurality of pre-defined data fields know to berelevant to a course of care of a patient undergoing labor. In anotherexample, a graphical user interface that facilitates tracking a patientsuffering from acute coronary syndrome can include a plurality ofpre-defined data fields know to be relevant to a course of care of apatient suffering from acute coronary syndrome. In yet another example,a user can provide input defining respective data fields associated witha course of patient care. According to this example, a user can add anynumber N of data fields to correspond to a relevant patient condition orpatient care event.

In an aspect, data fields can be added (e.g., by a user orautomatically) as needed over the course of patient care. For example,each time a new drug is administered to the patient, a new data fieldcorresponding to the drug can be added. In another aspect, a patientcare tracking interface (e.g., interface 100) can be configured to adddata fields in response to occurrence of a patient care event/conditionor characteristic of the event/condition. For example, when a newpatient condition occurs (e.g., as determined by a medical caregiver orsystem configured to monitor patient conditions), a patient trackingtool responsible for generating interface 100 can create a new datafield to correspond to the patient condition. The patient tracking toolcan also automatically fill a cell included in the data fieldcorresponding to a time associated with the new patient condition. Inanother example, the patient tracking tool can add data fields over thecourse of care based on anticipated patient conditions or events. Forexample, the patient tracking tool can determine, based on occurrence ofcondition “ABC” at time TA, condition “XYZ” is likely to occur at timeT_(B), (where time T_(B) follows time TA). The patient tracking tool canthen generate a new data field corresponding to condition “XYZ.” In yetanother example, the patient tracking tool can automatically add datafields based on a predefined relationship between a data field selectedfor a patient care event or patient condition and other patient careevents or patient conditions. For example, where a data field is addedthat corresponds to a patient care event “DEF,” data interacting toolcan be configured to add one or more additional sub-data fields relatedto patient care event “DEF.”

In addition to data fields corresponding to patient care events orpatient conditions, interface 100 can be configured to automatically addcolumns corresponding to new points or segments of time as the points orsegments of time occur. For example, each time a new period of 4 hourspasses or is initiated, interface 100 can generate a new columncorresponding to the new period of 4 hours. It should be appreciatedthat columns associated with the horizontal timeline axis can beassociated with various increments of time and are not limited to 4 hourincrements. For example, columns associated with axis 102 canrespectively correspond to sequential time segments of 15 minutes, 30minutes, one hour, two hours, etc.

As previously noted, in one aspect, a user can select a specific row,column or cell and input data (e.g., a color, text, a symbol) into thespecific row, column or cell. For example, a user can select a cellcorresponding to a patient care event or condition occurring at aparticular point in time and input data or fill the cell to identifyoccurrence and/or a characteristic of the patient care event orcondition. In another example, only those cells associated with acurrent point in time can be activated for selection/receipt of input.According to this example, a user cannot go back in time and changepreviously entered data and/or skip ahead in time to input data. Alsoaccording to this example, because data input for a particular datafield will be automatically associated with a cell corresponding to acurrent point in time, rather than selecting the cell, the user canmerely select the data field for which input is desired. For example, auser can provide input (or the input can be received automatically froma medical device or other device) indicating the patient's currenttemperature is 37.2° C. Based on timing of receipt of the input, alogging component associated with interface 100 can automatically enterthe input into the appropriate cell located at a column corresponding tothe timing of receipt and a row or data input field corresponding totemperature (e.g., data input field/row 124 at column 16 hours). In anaspect, in order to facilitate efficient entry of data into interface100, one or more data fields or cells can be associated with a drop downmenu that is activated upon selection of the data field or cell. Thedrop down menu can provide various data input options that can beselected for entry into the data field or cell.

FIG. 2 presents an example device 200 having a patient monitoring module204 for generating a patient tracking interface (e.g., interface 100 andthe like) in accordance with aspects and embodiments described herein.Device 202 can include memory 220 for storing computer executablecomponents and instructions and processor 222 to facilitate operation ofthe instructions (e.g., computer executable components and instructions)by system device 202. Repetitive description of like elements employedin respective embodiments of systems, device, and interfaces describedherein are omitted for sake of brevity.

As used in this disclosure, the terms “content consumer” or “user”refers to a person, entity, system, or combination thereof. For example,the term user is often employed herein to refer to a medical worker thatprovides input for inclusion in a patient tracking interface. Device 202can include any suitable computing device associated with a user andconfigured to execute patient monitoring module 204 and/or provide apatient tracking interface (e.g., interface 100 and the like) inaccordance with aspects described herein. For example, device 202 caninclude but is not limited to, a desktop computer, a laptop computer, aserver, a cellular phone, a smartphone, a tablet personal computer (PC),or a personal digital assistant (PDA).

Patient monitoring module 204 is configured to generate a patienttracking interface (e.g., interface 100) as described herein. Device 202can include presentation component 218 to display the patient trackinginterface (e.g., via a display screen) to a user. For example, patientmonitoring module 204 can generate patient tracking interface 100 (andthe like) at device 202 and present interface 100 via a display screenassociated with device 202. Additional examples of patient trackinginterfaces in accordance with aspects described herein are presented inFIGS. 3-8B.

Patient monitoring module 204 can include reception component 206,interface component 208, logging component 220, time component 212 andsecurity component 214. Interface component 206 is configured togenerate an interface that facilitates tracking a course of care of apatient, such as patient tracking interface 100. The various features ofinterfaces capable of generation by interface component 206 aredescribed in association with the example interfaces provided in FIG. 1and FIGS. 3-8B. However common features of the various interfacescapable of generation by interface component 206 include a plurality ofinput compartments defined by a first axis having columns correspondingto sequential points in time and a second axis having rows respectivelycorresponding to patient care events or patient conditions associatedwith a course of patient care.

Reception component 208 is configured to receive input regarding apatient care event or condition that occurred over a course of patientcare for which a patient tracking interface is configured to track. Forexample, reception component 208 can receive input directed towards aparticular cell/compartment of a patient tracking interface indicatingoccurrence and/or a characteristic of a patient care event or patientcondition represented by the cell/compartment at a time corresponding tothe cell/compartment. In another example, reception component 208 canreceive input merely identifying occurrence and/or a characteristic of apatient care event or patient condition. According to this example,based on the received input, logging component 210 can provide data(e.g., text, a color, a symbol) into the appropriate cell or cells of apatient tracking interface that correspond to the patient care event orpatient condition at the time at which the input was received. The datacan include text, a fill color, and/or a symbol representative of theoccurrence and/or a characteristic of the patient care event or patientcondition. In an aspect, where input is received for a new patient careevent or condition that is not represented by the patient trackinginterface, interface component 206 can automatically generate a new datainput field/row corresponding to the new patient care event orcondition. Reception component 208 can also receive user input defininga data input field/row for inclusion in a patient tracking interfaceand/or defining time segments for association with respective columns ofthe patient tracking interface.

Information received by reception component 206 can be provided by auser or a remote device (e.g., a remote medical device). For example, auser can provide input data directly into a row, column orcell/compartment of a patient tracking interface. In another example, auser can merely provide information indicating occurrence and/or acharacteristic of a patient care event or patient condition. In anotherexample, information identifying occurrence and/or a characteristic of apatient care event or patient condition can be received from a medicaldevice associated with the patient. According to this example, themedical device can be configured to send information identifyingoccurrence and/or a characteristic of the patient care event or patientcondition to reception component. In an aspect, reception component 206is configured to receive information regarding occurrence and/or acharacteristic of a patient care event or patient condition in real timeover the course of patient care.

Logging component 210 is configured to fill one or more inputcompartments of a patient tracking interface (e.g., interface 100 andthe like) in response to input received by reception component. In anaspect, logging component 210 can fill one or more input compartments ofa patient tracking interface that respectively corresponding to a pointor period of time associated with occurrence of a patient care event orpatient condition in response to reception input identifying occurrenceof the patient care event or patient condition. For example, in responseto reception of information indicating intravenous magnesium was startedon the patient at time of 1:23 pm, logging component 210 can input datainto a cell/compartment of the patient tracking interface correspondingto a data input field/row for intravenous magnesium at time of 1:23 pm.The data can include text, color, and/or a symbol indicating thatintravenous magnesium has been administered.

In another aspect, logging component 210 can fill one or more inputcompartments of a patient tracking interface that respectivelycorresponding to a point or period of time associated with occurrence ofa patient care event or patient condition with data representative of acharacteristic of the patient care event or patient condition inresponse to reception of input identifying the characteristic. Forexample, in response to reception of information identifying a degree ofdilation of 3 cm of a patient at time 12:45 pm, logging component 210can input data into a cell/compartment of the patient tracking interfacecorresponding to a data input field/row for dilation at time 12:45 pm.The data can include text, color, and/or a symbol indicating the patienthas a degree of dilation of 3 cm.

Time component 212 is configured to track progression of time over thecourse of care. For example, time component 212 can include a clock thatidentifies a time when patient care begins and tracks passage of timeover the course of care. Time component 212 can determine a currentpoint in time, and/or an amount of time passed following initiation ofthe course of care, associated with receipt of information identifyingoccurrence and/or a characteristic of a patient care event or patientcondition. In turn, logging 210 can determine the appropriate area of atimeline (e.g., column) to include data identifying the occurrenceand/or a characteristic of the patient care event or patient conditionbased in part on a time of receipt of the input.

In an aspect, received input regarding a patient care event or patientcondition identifies a time of onset of a patient care event or patientcondition that is ongoing. According to this aspect, time component 212can track progression of time over the course of care following receiptof the input and logging component 208 can automatically fill inputcompartments of a row corresponding to the patient care event or patientcondition over the course of care until new input is received thatidentifies a change in the patient care event or patient condition oruntil the course of patient care ends. For example, following receipt ofdata indicating that a patient has entered stage I of labor, loggingcomponent 208 can automatically fill compartments/cells of a rowcorresponding to stage I of labor to indicate that the patient iscurrently in stage I of labor as time progresses until new informationis received that the patient is not longer in stage I of labor. Inanother aspect, following receipt of data indicating that a patient careevent or patient condition (e.g., ROM) has occurred, logging component208 can automatically fill compartments/cells of a row corresponding tothe patient care event or patient condition to indicate an amount oftime elapsed following occurrence of the patient care event or patientcondition.

Security component 214 is configured to restrict access to a patienttracking interface and/or restrict devices/users from which informationcan be received for input into a patient tracking interface. Forexample, security component 214 can provide aauthentication/authorization mechanism that allows only authorized users(medical staff) to access and/or manipulate data associated with apatient tracking interface (e.g., interface 100 and the like).

Device 202 can include presentation component 218 to present or displaya patient tracking interface generated/configured by interface component208. Presentation component 218 can present a patient tracking interface(e.g., interface 100 and the like) for use with any suitable type ofcomputing device, for example a mobile phone, a tablet computer, adesktop computer, a server system, a personal computer, a cable set topbox, satellite set top box, a television set, or an internet-enabledtelevision. The respective devices listed above often have differentcapabilities and limitations (e.g., screen size, decoders . . . ). In anaspect, presentation component 120 can provide presentation options inaccordance with different device capabilities or limitations. Forexample, data rendering capabilities may be more limited in a mobiledevice (e.g., a smart-phone) than in a fixed computing device (e.g., adesktop computer). In addition, because displays of various mobiledevices are often smaller than displays in fixed computing devices, itmay be possible only to display a relatively small amount of informationat any given time on a mobile device.

In view of the above, presentation component 218 can present patienttracking interfaces generated/configured by interface component 208 invarious formats and/or in accordance with various display mediums. Inparticular, presentation component 218 can adapt and optimize display ofoptions and content based on respective rendering device capabilities(e.g., based on screen size, screen resolution, input capabilities ofthe devices, processing capabilities etc.). For example, presentationcomponent 208 can adapt the size, shape, and number of columns, rowsand/or cells displayed or included in a patient tracking interface basedon the size and orientation of a display screen of a device at which thepatient tracking interface is displayed.

Input component 216 is configured to facilitate user interaction with apatient tracking interface displayed at device 202. In particular, inputcomponent 216 can be configured to receive commands from an input deviceassociated with device 202 (e.g., a controller, a keyboard, a mouse, atouch screen, voice recognition input device, a gesture recognitioninput device, etc., (not shown)), and interpret those commands tofacilitate user interaction with a patient tracking interface displayedat device 202. For example, input component 216 can receive commandsfrom a user to define a data field or row, to add a data field or row,to define time segments for representation by respective columns of thetimeline, to add columns, or to provide data input to fill cells of thepatient tracking interface (e.g., with text, a color, a symbols, etc.).For example, input component 216 can include a touch screen display thatallows a user to touch various parts of a patient tracking interface toprovide data input associated with the various parts. In anotherexample, input component 216 can include a voice recognition inputdevice that can identify and interpret voice commands regarding fillinga patient tracking interface with data.

FIGS. 3-7 present examples of various graphical user interfaces thatfacilitate tracking information related to a course of patient care. Inparticular, FIGS. 3-7 demonstrate an example patient tracking interfaceas it evolves from a default shell or form in response to receipt ofinput regarding care of a patient over the course of care of thepatient. Although these example interfaces demonstrate tracking patientcare events and conditions associated with a course of labor, it shouldbe appreciated that various aspects of the interfaces can be employed totrack other type of patient care scenarios. Further, it should beappreciated that the patient care events and conditions monitored inthese example interfaces are not intended to limit the scope of possiblepatient care events and conditions that can be monitored via the subjectpatient tracking tool. In particular, a data field provided in row ofthe interfaces described herein can be adapted to correspond to anypossible patient care event or condition associated with a course oflabor. In addition, one or more of the data fields provided in therespective interfaces can be removed and/or additional data fields canbe added. Repetitive description of like elements employed in respectiveembodiments of systems and interfaces described herein are omitted forsake of brevity.

With reference initially to FIG. 3 , presented is an example shellpatient tracking interface 300 in accordance with aspects andembodiments described herein. Interface 300 includes a plurality ofcompartments (e.g., the cells/compartments collectively identified bynumeral 312) defined by a first axis 310 having columns corresponding tosequential periods (e.g., 4 hour periods) of time over the course ofpatient care and a second axis 308 having one or more rows respectivelycorresponding to one or more patient care events or patient conditions.In particular, row 302 corresponds to admittance of the patient. Rows304 and 306 include undefined fields. In an aspect, a user can selectrow 304 and/or row 306 to define a data field for the row associatedwith a patient care event or patient condition. It should be appreciatedthat any number N of data fields/rows can be added.

In an aspect, interface 300 can be modified or configured to track anycourse of patient care that involves caring for a patient over a periodof time. According to this aspect, the data fields or rows can be fullyor partially defined by a user. In another aspect, interface 300 can beconfigured for tracking a specific course of patient care (e.g., labor).According to this aspect, one or more of the data fields/rows can bepreconfigured to represent a known patient care event and/or patientcondition associated with the specific course of care.

In addition, one or more data fields/rows can be preconfigured forinclusion in interface 300 in response to occurrence of a predeterminedevent or condition. According to this aspect, information definingrelationships between patient care events and patient conditions for acourse of patient care, and/or characteristics of the patient careevents or conditions (e.g., stored in memory 220), can direct automaticaddition of data fields to interface 300 (e.g., by interface component206). For example, in response to addition/inclusion of a data field tointerface 300 corresponding to a first patient care event or patientcondition, one or more additional sub-data fields related to ordependent on the first patient care event or condition can beautomatically added to interface 300 (e.g., by interface component 206).In another example, in response to receipt of data associated withoccurrence and/or a characteristic of a first patient care event orpatient condition, one or more additional sub-data fields related to theoccurrence or the characteristic of the first patient care event orcondition can be added. For instance, if a patient has a temperatureabove X degrees, based on known factors related to the patient and thecourse of care, an appropriate medical response can includeadministration of drug Y. Accordingly, in response to received dataindicating the patient has a temperature above X degrees, a data fieldcorresponding to administration of drug Y can automatically be added tointerface 300. Still in yet another example, one or more data fields canbe automatically added to interface 300 in response to passage ofvarious amounts of time in view of a course of patient care for whichthe interface is configured to track. For example, in association with aparticular course of care, after the patient has been admitted 8 hours,the patient should receive X and Y treatment. Thus in response topassage of 8 hours following admittance, data fields for treatments Xand Y can be added to interface 300 automatically (e.g., via interfacecomponent 206).

FIG. 4 depicts another exemplary patient tracking interface 400 inaccordance with aspects and embodiments described herein. Interface 400is specifically configured to track the course of care of a patientthroughout labor. In an aspect, interface 400 is an extension ofinterface 300 following admittance of a patient for 8 hours. Accordingto this aspect, default data fields 304 and 306 of interface 300 haverespectively been changed to data fields 402 and 404. Data field 402corresponds to stages of labor and data field 404 corresponds tocategories of labor. Stages of labor and categories of labor can includestages and categories of labor associated with a condition of the motherand/or the infant. For exemplary purposes, date input field 402corresponding to stages of labor indicates a descriptive stage of astate associated with the infant and input field 404 corresponding tocategories of labor indicates a descriptive category of a stateassociated with the mother. In an aspect, data fields 402 and 404 aredefined by a user. In another aspect, data fields 402 and 404 areautomatically created in response to receipt of input indicating thepatient has been admitted and input tailoring interface 400 for trackinglabor of a patient.

In an aspect, upon admittance of the patient, information is receivedindicating she has been admitted, has entered category 1 of labor andher infant is in stage 1. For example, this information can be enteredby a medical caregiver. In response to entry of the information, colorbars 406, 408 and 410 are respectively initiated or generated (e.g., bylogging component 210). Color bars 406, 408 and 410 are configured torepresent timelines respectively indicating amount of elapsed time thefollowing admittance of the patient, duration of time the infant is instage 1, and duration of time the patient is in category 1 of labor. Inan aspect, color bar 406 is configured to automatically continuehorizontally (e.g., to the right) across interface 400 in response topassage of time until information is received indicating the patient isno longer admitted. Similarly, color bars 408 and 410 can also beconfigured to automatically continue horizontally (e.g., to the right)across interface 400 until new information is received indicating theinfant is no longer in stage 1 or the patient is in category 1 of labor,respectively.

FIG. 5 depicts another exemplary patient tracking interface 500 inaccordance with aspects and embodiments described herein. In an aspect,interface 500 is an extension of interface 400 following admittance ofthe patient for 12 hours. Interface 500 includes a new data field 502corresponding to ROM. Interface 500 further includes a new color bar 504indicating that the patient's membranes ruptured following 8 hours ofadmittance (e.g., or sometime between 8 and 12 hours after admittance).In an aspect, data field 502 and color bar 504 was added to interface500 based on user input defining and adding the data field andindicating that the patient's membrane ruptured at a time between 8 and12 hours of time following admittance of the patient. In another aspect,data field 502 and color bar 504 was added to interface 500 in responseto receipt of input indicating that the patient's membrane ruptured at atime between 8 and 12 hours of time following admittance of the patient.

As seen when comparing interfaces 400 and 500, color bars 406, 408 and410 have automatically (e.g., without additional user input) extendedhorizontally across interface 500 in response to passage of time. In anaspect, color bar 504 is also configured to automatically continuehorizontally (e.g., to the right) across interface 500 in response topassage of time until information is received indicating the patient isno longer admitted.

FIG. 6 depicts another exemplary patient tracking interface 600 inaccordance with aspects and embodiments described herein. In an aspect,interface 600 is an extension of interface 500 following admittance ofthe patient for 20 hours. Interface 600 includes a new data field 602corresponding to Cytotec. Interface 600 further includes a new color bar604 indicating that the patient was administered cytotec between 16 and20 hours following admittance and new color bar 606 indicating thepatient has entered category II of labor. In an aspect, data field 602and color bar 604 was added to interface 600 based on user inputdefining and adding the data field and indicating that the patient wasadmitted cytotec between 16 and 20 hours following admittance. Inanother aspect, data field 602 and color bar 604 was added to interface600 in response to receipt of input indicating that the patient wasadministered cytotec between 16 and 20 hours following admittance. Inaddition, color bar 410 was capped and color bar 606 was initiated inresponse to receipt of new data indicating the patient has enteredcategory II of labor.

As seen when comparing interfaces 500 and 600, color bars 406, 408, 410and 504 have automatically (e.g., without additional user input)extended horizontally across interface 600 in response to passage oftime. In an aspect, color bar 604 is configured automatically continuehorizontally (e.g., to the right) across interface 600 in response topassage of time until information is received indicating the patient isno longer being administered cytotec. Similarly, color bar 606 can beconfigured to automatically (e.g., to the right) continue acrossinterface 600 in response to passage of time until information isreceived indicating the patient is no longer in category II of labor.

FIG. 7 depicts another exemplary patient tracking interface 700 inaccordance with aspects and embodiments described herein. In an aspect,interface 700 is an extension of interface 600 following admittance ofthe patient for 24 hours. Interface 700 includes a new data field 702corresponding to pitocin. Interface 700 further includes a new color bar704 indicating that the patient was administered pitocin between 20 and24 hours following admittance and new color bar 706 indicating theinfant has entered stage II. In an aspect, data field 702 and color bar704 was added to interface 700 based on user input defining and addingthe data field and indicating that the patient was admitted pitocinbetween 20 and 24 hours following admittance. In another aspect, datafield 702 and color bar 704 was added to interface 700 in response toreceipt of input indicating that the patient was administered pitocinbetween 20 and 24 hours following admittance. In addition, color bar 408was capped and color bar 706 was initiated in response to receipt of newdata indicating the infant has entered stage II.

As seen when comparing interfaces 600 and 700, color bars 406, 504, 604and 606 have automatically (e.g., without additional user input)extended horizontally across interface 700 in response to passage oftime. In an aspect, color bar 704 is configured automatically continuehorizontally (e.g., to the right) across interface 700 in response topassage of time until information is received indicating the patient isno longer admitted. Similarly, color bar 706 can be configured toautomatically (e.g., to the right) continue across interface 700 inresponse to passage of time until information is received indicating theinfant is no longer in stage II.

FIGS. 8A-8B, present another example patient tracking interface 800 inaccordance with aspects and embodiments described herein. Patienttracking interface 800 depicts a completed interface following trackingof a patient in labor over the course 25 hours and two days. FIG. 8Aincludes information for the first day (Jan. 7, 2014) and FIG. 8Bincludes information for the second day (Jan. 8, 2014). It should beappreciated that interface 800 is divided over FIGS. 8A and 8B merelyfor lack of space due to restrictions in page dimensions. In particular,interface 800 can be displayed as a single continuous chart. Bar 802 isprovided as a marker to indicate how interface 800 in FIG. 8A connectsto interface 800 in FIG. 8B.

Interface 800 includes a plurality of compartments (defined by a firstaxis 804 having columns corresponding to sequential hours of time (inmilitary time) and/or sequential hours passed, and a second axis 806having a plurality of rows respectively corresponding to patient careevents and patient conditions. In particular, row 808 corresponds todecision to induce. Data included in row 808 depicts the actual elapsedtime from onset of induction. For example, grey color bar 828 marks theelapsed time following the decision to induce. In an aspect, grey colorbar 828 moved horizontally across row 808 with each passing hour markedas a fixed point following initial data input indicating the decision toinduct at time 1500.

Row 810 corresponds to active phase. Data included in row 810 depictsthe actual elapsed time from the beginning of the active phase of labor.For example, green color bar 830 marks the elapsed time followingbeginning of active phase. In an aspect, green color bar 830 movedhorizontally across row 810 with each passing hour marked as a fixedpoint following initial data input indicating the beginning of activephase at time 2100.

Row 812 corresponds to rupture of membranes. Data included in row 820depicts the actual elapsed time following rupture of the patientsmembranes. For example, beige color bar 832 marks the elapsed timefollowing rupture of membranes. In an aspect, beige color bar 832 movedhorizontally across row 812 with each passing hour marked as a fixedpoint following initial data input indicating the rupture of membranesat time 2400.

Row 814 corresponds to induction pharmaceutical. Data included in row814 depicts blocks of time during which an induction pharmaceutical wasadministered. For example, yellow bar 834 indicates that a first dose ofcytotec was administered beginning at time 1500 and ending at time 1600.Yellow bar 836 indicates a second dose of cytotec was administeredbeginning at time 2000 and ending at time 2300. In an aspect, varioustypes of induction pharmaceuticals can be administered to a patient.Accordingly, text can also be included in association with data input torow 814 (e.g., the yellow fill) to indicate which inductionpharmaceutical was administered. In an aspect, data field/row 814 caninclude a drop down menu that is displayed upon selection of datafield/row 814 and provides options of induction pharmaceuticals toselect from for ease of date entry. In another aspect, differentinduction pharmaceuticals can be associated with different fill colors.

Row 816 corresponds to oxytocin. Data included in row 816 depicts blocksof time during which oxytocin was administered. For example, grey bar838 indicates that a first dose of oxytocin was administered beginningat time 2300 on Jan. 7, 2014 and ending at time 100 on Jan. 8, 2014.Grey bar 844 indicates a second dose of oxytocin was administeredbeginning at time 700 and ending at time 1400 on Jan. 8, 2014. In anaspect, an oxytocin is an intravenous drug that can be started andstopped multiple times during the course of labor. Grey bars 838 and 844can indicate blocks of time when the drug is infusing. Text dataindicating the “rate of infusion” can also be included in associationwith respective fill blocks indicating times when the drug is infused.In an aspect, text data indicating rate of infusion can be included whenthe rate of infusion is above a threshold rate (e.g., 20 or greater).

Row 818 corresponds to dilation. Data included in row 818 depicts blocksof time during which the patient was dilated. For example, pink colorbar 840 indicates blocks of time during which the patient was dilated,beginning at 2300 on Jan. 7, 2014. Text data can be associated withfixed cells indicating a degree of dilation of the patient at therespective times associated with the cells (e.g., 1 cm, 2 cm, 3 cm,etc.).

Row 820 corresponds to fetal heart rate. Data included in row 820depicts a measured baseline fetal heart rate that includes a fixednumber of beats per minute. In an aspect, after the baseline fetal heartrate is selected and/or entered, a color bar (e.g., blue color bar 842)is initiated and moves across row 820 as time passes to indicate whatthe baseline fetal heart rate was.

Row 822 corresponds to deceleration of the fetal heart rate. Dataincluded in row 822 is entered in response to a deceleration of thefetal heart rate from the baseline fetal heart rate. For example, acolor bar (e.g., red color bar 836) can be generated to indicate a fixedtime or time period during which the fetal heart rate decelerates. In anaspect, data is entered in row 822 in response to deceleration of thefetal heart rate for a period of time greater than 2 minutes.Information indicating a total amount of time during which the fetalheart rate decelerated can also be included in associated with a fillcolor in row 822.

Row 824 corresponds to maternal temperature. Data included in row 824can include a fixed color bar indicating a point in time or period oftime during which the maternal temperature exceeded a thresholdtemperature (e.g., 38° C.). In an aspect, in response to entry of datain row 824, interface 800 can be configured to generate a pop-up displayasking the caregiver if an antibiotic was administered. The caregivercan then provide additional input indicating whether an antibiotic wasadministered or not and what type of antibiotic was administered if anantibiotic was administered. In an aspect, this additional informationcan be associated with the color block included in row 824 associatedwith the spike in temperature. In another aspect, in response to anindication that an antibiotic was administered, interface 800 cangenerate an additional data field/row corresponding to the antibioticand information regarding administration of the antibiotic can beincluded in this new data field/row.

Row 828 corresponds to maternal hypertension or blood pressure. Dataincluded in row 828 can include a fixed color bar indicating a point intime or period of time during which the maternal blood pressure (e.g.,systolic or diastolic) increased or decreased with respect to thresholdvalues. In an aspect, in response to a second increase in blood pressureabove a threshold value, interface 800 can be configured to generate apop-up display asking the caregiver if intravenous magnesium is to bestarted. The caregiver can then provide additional input indicatingwhether intravenous magnesium was administered or not. In an aspect,this additional information can be associated with row 828 where data isprovided indicating the rise in blood pressure. In another aspect, inresponse to an indication that intravenous magnesium was started,interface 800 can generate an additional data field/row corresponding tointravenous magnesium and a color bar can be generated in thisadditional data field/row indicating the amount of time intravenousmagnesium was provided.

FIG. 9 presents an example system 900 for generating and presenting apatient care tracking interface in accordance with aspects andembodiments described herein. Repetitive description of like elementsemployed in respective embodiments of systems and interfaces describedherein are omitted for sake of brevity.

System 900 includes device 202 and one more external data input sources902. As previously noted, data input received by reception component 208can be received from a user (e.g., a medical caregiver) and/or anexternal device, such as a medical device. For example, a user can inputdata, (e.g., via input component 216) directly into a patient trackinginterface generated by interface component 206 using various inputdevices (e.g., a touch screen, soft keys, a keypad/keyboard, voicerecognition software, etc.). In an aspect, the user can employ a remotedevice to provide data to reception component 208. According to thisaspect, an external data source 902 can include a remote control orremote device that allows a user to send (e.g., either via a wired orwireless data connection) data input to patient monitoring module 204for entry into a patient tracking interface. For example, the user canemploy a remote tablet computer or smartphone to wirelessly transmitdata for input to a patient tracking interface via a local area network(LAN).

In another aspect, an external data input source 902 can include aremote medical device associated with the patient. The remote medicaldevice can sense patient conditions/events and send sensed data input topatient monitoring module 204 for input to a patient tracking interfacegenerated by interface component 206 and configured to track a course ofcare of the patient. The medical device can send data to patientmonitoring module 204 via a wired or wireless data connection. In anaspect, the medical device can send the data via a LAN, a personal areanetwork (PAN, e.g., using near field communication, Bluetooth™communication, etc.), or a wide area network (WAN). Some exemplarymedical devices that can automatically provide data input for entry intoa patient tracking interface generated by interface component 206 caninclude but are not limited to: a vital signs monitoring device, a heartmonitor device, a pulse oximeter device, a maternal contraction monitordevice, a capnograph, a blood gas monitor device, and a respiratoryassistance device.

FIG. 10 presents another example system 1000 for generating andpresenting a patient care tracking interface in accordance with aspectsand embodiments described herein. System 1000 is similar to system 900with the addition of tracking/alert component 1002 and inferencecomponent 1004 to patient monitoring module 204. Repetitive descriptionof like elements employed in respective embodiments of systems andinterfaces described herein are omitted for sake of brevity.

Tracking/alert component 1002 is configured to analyze a patienttracking interface based on data entered therein, a course of patientcare, and a current point in time to facilitate determining or inferringclinical decisions associated with caring for the patient. Inparticular, tracking/alert component 1002 can employ various algorithmsand information sources that define relationships between patientconditions, patient care events, and a course of patient care todetermine or infer clinical decisions regarding caring for the patientand/or to determine or infer issues associated with a condition of thepatient.

In an aspect, tracking/alert component 1002 can determine or infer whendata is missing from a patient tracking interface regarding a patientcare event or patient condition based on relationships between patientcare events and/or patient care conditions, a course of patient care,and a current point in the course of the patient care. In response to adetermination of missing data regarding a patient care event or patientcondition, tracking/alert component 1002 can call attention to a medicalcaregiver to perform the patient care event and/or check and enterinformation regarding the patient condition.

For example, tracking/alert component 1002 can determine or infer thatbased on a course of patient care and a current point in time, datashould have been received regarding occurrence of patient care event“WRT.” Accordingly, patient tracking/alert component can notify amedical caregiver to perform patient care event “WRT” and enter dataregarding performance of the patient care event. In another example,tracking/alert component 1002 can determine or infer that based on datareceived indicating patient care event “UYT” was performed, informationregarding patient condition “345” should have been received.Accordingly, patient tracking/alert component 1002 can notify a medicalcaregiver to check patient condition “345” and enter data regarding thepatient condition. In yet another example, tracking/alert component 1002can determine or infer that based on data indicating a patient conditionhas fallen below an unsatisfactory level, information regardingperformance of a patient care event “JHG” should have be received.Accordingly, patient tracking/alert component can notify a medicalcaregiver to perform patient care event “JHG” and enter data regardingperformance of the patient care event.

In another aspect, tracking/alert component 1002 can determine or inferissues associated with a patient condition based on relationshipsbetween patient care events and/or patient care conditions, a course ofpatient care, and a current point in the course of the patient care. Forexample, patient tracking/alert component 1002 can analyze data enteredinto a patient tracking interface and infer or determine that based onthe collective information, the patient is in an unsatisfactory state.For instance, patient tracking/alert component 1002 can determine orinfer that based on data regarding various vital signs of the patientand/or the infant and information indicating drug “XCR” wasadministered, the patient should be responding in a different manner. Inresponse to a determination of an unsatisfactory patient state based ondata received or entered into a patient tracking interface,tracking/alert component 1002 can call attention to a medical caregiverand notify the medical caregiver of the unsatisfactory state of thepatient and the basis for the determination that the patient is in anunsatisfactory state.

In an exemplary embodiment, tracking/alert component 1002 can monitorvarious tracked patient care event and tracked conditions of the patientand infant to determine when a cesarean section (C-section) should beperformed. For example, tracking/alert component 1002 can determine,(using various preconfigured algorithms defining relationships betweenpatient care events and conditions/states of the mother and infant),that based on a current state of the mother and/or infant and based onprevious patient care events and conditions leading up to the currentpoint in time (e.g., including time elapsed associated with patient careevents and conditions), that a C-section should be performed.

Tracking/alert component 1002 can employ various techniques to notify amedical caregiver regarding missing data from a patient trackinginterface and/or regarding an issue associated with a state or conditionof the patient. For example, patient tracking/alert component 1002 canhighlight a data field/row or cell associated with missing informationto call attention of the medical caregiver to that data field/row andindicate that information is missing therefrom. In another example, thepatient tracking alert component 1002 can cause the data field/row orcell to flash. In an aspect, where the missing information is associatedwith a patient care event or patient condition for which a datafield/row is not provided in the patient tracking interface,tracking/alert component 1002 can instruct interface component to createor add the data field/row.

In another example, tracking/alert component 1002 can sound an alarm tonotify a medical caregiver regarding missing data from a patienttracking interface and/or regarding an issue associated with a state orcondition of the patient. In yet another example, tracking/alertcomponent 1002 can send a notification message to the medical caregiver(e.g., in the form of an electronic message such as a text message, anemail, or other form of electronic message) regarding missing data froma patient tracking interface and/or regarding an issue associated with astate or condition of the patient.

Inference component 1004 is configured to provide for or aid in variousinferences or determinations associated with aspects of patientmonitoring module. For example, inference component 1004 can infer wheninterface component 208 should add an additional data field/row for apatient care event or patient condition based on relationships betweenpatient care events and/or patient care conditions, a course of patientcare, and a current point in the course of the patient care. In anotherexample, inference component 1004 can facilitate tracking/alertcomponent 1002 with various inferences regarding identifying missingdata from a patient tracking interface and/or determining an issueassociated with a state or condition of the patient. In aspect, all orportions of device 202 can be operatively coupled to inference component1002. Moreover, inference component 1002 can be granted access to all orportions of external systems/sources (e.g., external data input sources902 and other external systems).

In order to provide for or aid in the numerous inferences describedherein, inference component 1002 can examine the entirety or a subset ofthe data to which it is granted access and can provide for reasoningabout or infer states of the system, environment, etc. from a set ofobservations as captured via events and/or data. An inference can beemployed to identify a specific context or action, or can generate aprobability distribution over states, for example. The inference can beprobabilistic—that is, the computation of a probability distributionover states of interest based on a consideration of data and events. Aninference can also refer to techniques employed for composinghigher-level events from a set of events and/or data.

Such an inference can result in the construction of new events oractions from a set of observed events and/or stored event data, whetheror not the events are correlated in close temporal proximity, andwhether the events and data come from one or several event and datasources. Various classification (explicitly and/or implicitly trained)schemes and/or systems (e.g., support vector machines, neural networks,expert systems, Bayesian belief networks, fuzzy logic, data fusionengines, etc.) can be employed in connection with performing automaticand/or inferred action in connection with the claimed subject matter.

A classifier can map an input attribute vector, x=(x1, x2, x3, x4, xn),to a confidence that the input belongs to a class, such as byf(x)=confidence(class). Such classification can employ a probabilisticand/or statistical-based analysis (e.g., factoring into the analysisutilities and costs) to prognose or infer an action that a user desiresto be automatically performed. A support vector machine (SVM) is anexample of a classifier that can be employed. The SVM operates byfinding a hyper-surface in the space of possible inputs, where thehyper-surface attempts to split the triggering criteria from thenon-triggering events. Intuitively, this makes the classificationcorrect for testing data that is near, but not identical to trainingdata. Other directed and undirected model classification approachesinclude, e.g., naïve Bayes, Bayesian networks, decision trees, neuralnetworks, fuzzy logic models, and probabilistic classification modelsproviding different patterns of independence can be employed.Classification as used herein also is inclusive of statisticalregression that is utilized to develop models of priority.

FIG. 11 presents another example system 1100 for generating andpresenting a patient care tracking interface in accordance with aspectsand embodiments described herein. Repetitive description of likeelements employed in respective embodiments of systems and interfacesdescribed herein are omitted for sake of brevity.

Similar to systems 900 and 1000, system 1100 includes a device (e.g.,server device 1102 having a patient monitoring module 204 and one ormore external data input sources 902. Server device 1102 can includesimilar features and functionalities as device 202. For example, serverdevice 1102 can input component 1104 and presentation component 1106.Input component 1104 and presentation component 1106 can operate inaccordance with input component 216 and presentation component 218,respectively. However, unlike device 202 of systems 900 and 1000, serverdevice 1102 can include communication component 1108. Communicationcomponent 1108 is configured to make one or more aspects of patientmonitoring module 204 available to one or more other devices (e.g.,client device 1110 and/or client device 118) via one or more networks1114. Network(s) 1114 can include wired and wireless networks, includingbut not limited to, a cellular network, a wide area network (WAD, e.g.,the Internet), a local area network (LAN), or a personal area network(PAN). For example, client device 1118 can communicate with mediaprovider server device 1102 (and vice versa) using virtually any desiredwired or wireless technology, including, for example, cellular, WAN,wireless fidelity (Wi-Fi), Wi-Max, WLAN, and etc.

For example, server device 1102 can configure and/or generate a patienttracking interface (e.g., interface 100 and the like) and provide otherdevices (e.g., client device 1110 and client device 1118) access to theinterface via a network 1114. The other devices can display theinterface via a presentation component (e.g., presentation component1112 or 1124 of devices 1110 and 1118 respectively) provided thereon.For example, presentation component 1112 and/or 1124 can access apatient tracking interface configured and stored at the server device1102 using a browser or web application associated therewith.

In an aspect, users of the other devices can merely view a patienttracking interface hosted by server device 1102 via a network. Forexample, client device 1110 can view, via a network 1114 usingpresentation component 1112, a patient tracking interface generated atthe server device 1102 as it is updated in real time. In another aspect,users of other devices can interact with a patient tracking interfacehosted by server device 1102. For example, client device 1118 caninclude a client version of patient monitoring module 204 and an inputcomponent 1122. According to this example, a user of client device canprovide data for input (e.g., via input component) into a patienttracking interface that is generated/configured at both the clientdevice 1118 and the server device 1102. The patient tracking interfaceat both devices can be updated to reflect the same data input in realtime.

In another aspect, communication component 1108 can be configured totransmit received data input associated with a patient trackinginterface generated by patient monitoring module to another device(e.g., client device 1110 and/or client device 1118). In response totransmission, the other can be device is configured to generate thepatient tracking interface.

In view of the example systems/interface described herein, examplemethods that can be implemented in accordance with the disclosed subjectmatter can be further appreciated with reference to flowcharts in FIGS.12-13 . For purposes of simplicity of explanation, example methodsdisclosed herein are presented and described as a series of acts;however, it is to be understood and appreciated that the disclosedsubject matter is not limited by the order of acts, as some acts mayoccur in different orders and/or concurrently with other acts from thatshown and described herein. For example, a method disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a method inaccordance with the subject specification. It should be furtherappreciated that the methods disclosed throughout the subjectspecification are capable of being stored on an article of manufactureto facilitate transporting and transferring such methods to computersfor execution by a processor or for storage in a memory.

FIG. 12 illustrates a flow chart of an example method 1200 forgenerating and presenting a patient tracking interface in accordancewith aspects and embodiments described herein. At 1202, an interface isgenerated that facilitates tracking a course of care of a patient (e.g.,via interface component 206). The interface includes a plurality ofinput compartments defined by a first axis having columns correspondingto sequential points in time over the course of the care and a secondaxis having rows respectively corresponding to patient care events orpatient conditions associated with the course of the care. At 1204,input is received regarding a patient care event or condition thatoccurred over the course of the care (e.g., via reception component208). At 1206, one or more input compartments respectively correspondingto a point or period of time associated with occurrence of the patientcare event or patient condition are filled in response to reception ofthe input.

FIG. 13 illustrates a flow chart of another example method 1300 forgenerating and presenting a patient tracking interface in accordancewith aspects and embodiments described herein. At 1302, an interface isgenerated that facilitates tracking a course of care of a patient (e.g.,via interface component 206). The interface includes a plurality ofinput compartments defined by a first axis having columns correspondingto sequential points in time over the course of the care and a secondaxis having rows respectively corresponding to patient care events orpatient conditions associated with the course of the care. At 1304,progression of time over the course of care is tracked (e.g., via timecomponent 212). At 1306, input is received identifying onset of apatient care event or patient condition that occurred over the course ofthe care (e.g., via reception component 208). At 1308, inputcompartments of a row corresponding to the patient care event or patientcondition are automatically filled over the course of care until newinput is received that identifies a change in the patient care event orpatient condition.

Example Operating Environments

The systems and processes described below can be embodied withinhardware, such as a single integrated circuit (IC) chip, multiple ICs,an application specific integrated circuit (ASIC), or the like. Further,the order in which some or all of the process blocks appear in eachprocess should not be deemed limiting. Rather, it should be understoodthat some of the process blocks can be executed in a variety of orders,not all of which may be explicitly illustrated in this disclosure.

With reference to FIG. 14 , a suitable environment 1400 for implementingvarious aspects of the claimed subject matter includes a computer 1402.The computer 1402 includes a processing unit 1404, a system memory 1406,a codec 1405, and a system bus 1408. The system bus 1408 couples systemcomponents including, but not limited to, the system memory 1406 to theprocessing unit 1404. The processing unit 1404 can be any of variousavailable processors. Dual microprocessors and other multiprocessorarchitectures also can be employed as the processing unit 1404.

The system bus 1408 can be any of several types of bus structure(s)including the memory bus or memory controller, a peripheral bus orexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, Industrial StandardArchitecture (ISA), Micro-Channel Architecture (MSA), Extended ISA(EISA), Intelligent Drive Electronics (IDE), VESA Local Bus (VLB),Peripheral Component Interconnect (PCI), Card Bus, Universal Serial Bus(USB), Advanced Graphics Port (AGP), Personal Computer Memory CardInternational Association bus (PCMCIA), Firewire (IEEE 1494), and SmallComputer Systems Interface (SCSI).

The system memory 1406 includes volatile memory 1410 and non-volatilememory 1412. The basic input/output system (BIOS), containing the basicroutines to transfer information between elements within the computer1402, such as during start-up, is stored in non-volatile memory 1412. Inaddition, according to present innovations, codec 1405 may include atleast one of an encoder or decoder, wherein the at least one of anencoder or decoder may consist of hardware, a combination of hardwareand software, or software. Although, codec 1405 is depicted as aseparate component, codec 1405 may be contained within non-volatilememory 1412. By way of illustration, and not limitation, non-volatilememory 1412 can include read only memory (ROM), programmable ROM (PROM),electrically programmable ROM (EPROM), electrically erasableprogrammable ROM (EEPROM), or flash memory. Volatile memory 1410includes random access memory (RAM), which acts as external cachememory. According to present aspects, the volatile memory may store thewrite operation retry logic (not shown in FIG. 14 ) and the like. By wayof illustration and not limitation, RAM is available in many forms suchas static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM),double data rate SDRAM (DDR SDRAM), and enhanced SDRAM (ESDRAM.

Computer 1402 may also include removable/non-removable,volatile/non-volatile computer storage medium. FIG. 14 illustrates, forexample, disk storage 1414. Disk storage 1414 includes, but is notlimited to, devices like a magnetic disk drive, solid state disk (SSD)floppy disk drive, tape drive, Jaz drive, Zip drive, LS-70 drive, flashmemory card, or memory stick. In addition, disk storage 1414 can includestorage medium separately or in combination with other storage mediumincluding, but not limited to, an optical disk drive such as a compactdisk ROM device (CD-ROM), CD recordable drive (CD-R Drive), CDrewritable drive (CD-RW Drive) or a digital versatile disk ROM drive(DVD-ROM). To facilitate connection of the disk storage devices 1414 tothe system bus 1408, a removable or non-removable interface is typicallyused, such as interface 1416.

It is to be appreciated that FIG. 14 describes software that acts as anintermediary between users and the basic computer resources described inthe suitable operating environment 1400. Such software includes anoperating system 1418. Operating system 1418, which can be stored ondisk storage 1414, acts to control and allocate resources of thecomputer system 1402. Applications 1420 take advantage of the managementof resources by operating system 1418 through program modules 1424, andprogram data 1426, such as the boot/shutdown transaction table and thelike, stored either in system memory 1406 or on disk storage 1414. It isto be appreciated that the claimed subject matter can be implementedwith various operating systems or combinations of operating systems.

A user enters commands or information into the computer 1402 throughinput device(s) 1428. Input devices 1428 include, but are not limitedto, a pointing device such as a mouse, trackball, stylus, touch pad,keyboard, microphone, joystick, game pad, satellite dish, scanner, TVtuner card, digital camera, digital video camera, web camera, and thelike. These and other input devices connect to the processing unit 1404through the system bus 1408 via interface port(s) 1430. Interfaceport(s) 1430 include, for example, a serial port, a parallel port, agame port, and a universal serial bus (USB). Output device(s) 1436 usesome of the same type of ports as input device(s). Thus, for example, aUSB port may be used to provide input to computer 1402, and to outputinformation from computer 1402 to an output device 1436. Output adapter1434 is provided to illustrate that there are some output devices 1436like monitors, speakers, and printers, among other output devices 1436,which require special adapters. The output adapters 1434 include, by wayof illustration and not limitation, video and sound cards that provide ameans of connection between the output device 1436 and the system bus1408. It should be noted that other devices and/or systems of devicesprovide both input and output capabilities such as remote computer(s)1438.

Computer 1402 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1438. The remote computer(s) 1438 can be a personal computer, a server,a router, a network PC, a workstation, a microprocessor based appliance,a peer device, a smart phone, a tablet, or other network node, andtypically includes many of the elements described relative to computer1402. For purposes of brevity, only a memory storage device 1440 isillustrated with remote computer(s) 1438. Remote computer(s) 1438 islogically connected to computer 1402 through a network interface 1442and then connected via communication connection(s) 1444. Networkinterface 1442 encompasses wire and/or wireless communication networkssuch as local-area networks (LAN) and wide-area networks (WAN) andcellular networks. LAN technologies include Fiber Distributed DataInterface (FDDI), Copper Distributed Data Interface (CDDI), Ethernet,Token Ring and the like. WAN technologies include, but are not limitedto, point-to-point links, circuit switching networks like IntegratedServices Digital Networks (ISDN) and variations thereon, packetswitching networks, and Digital Subscriber Lines (DSL).

Communication connection(s) 1444 refers to the hardware/softwareemployed to connect the network interface 1442 to the bus 1408. Whilecommunication connection 1444 is shown for illustrative clarity insidecomputer 1402, it can also be external to computer 1402. Thehardware/software necessary for connection to the network interface 1442includes, for exemplary purposes only, internal and externaltechnologies such as, modems including regular telephone grade modems,cable modems and DSL modems, ISDN adapters, and wired and wirelessEthernet cards, hubs, and routers.

Referring now to FIG. 15 , there is illustrated a schematic blockdiagram of a computing environment 1500 in accordance with thisdisclosure. The system 1500 includes one or more client(s) 1502 (e.g.,laptops, smart phones, PDAs, media players, computers, portableelectronic devices, tablets, and the like). The client(s) 1502 can behardware and/or software (e.g., threads, processes, computing devices).The system 1500 also includes one or more server(s) 1504. The server(s)1504 can also be hardware or hardware in combination with software(e.g., threads, processes, computing devices). The servers 1504 canhouse threads to perform transformations by employing aspects of thisdisclosure, for example. One possible communication between a client1502 and a server 1504 can be in the form of a data packet transmittedbetween two or more computer processes wherein the data packet mayinclude video data. The data packet can include a metadata, e.g.,associated contextual information, for example. The system 1500 includesa communication framework 1506 (e.g., a global communication networksuch as the Internet, or mobile network(s)) that can be employed tofacilitate communications between the client(s) 1502 and the server(s)1504.

Communications can be facilitated via a wired (including optical fiber)and/or wireless technology. The client(s) 1502 include or areoperatively connected to one or more client data store(s) 1508 that canbe employed to store information local to the client(s) 1502 (e.g.,associated contextual information). Similarly, the server(s) 1504 areoperatively include or are operatively connected to one or more serverdata store(s) 1510 that can be employed to store information local tothe servers 1504.

In one embodiment, a client 1502 can transfer an encoded file, inaccordance with the disclosed subject matter, to server 1504. Server1504 can store the file, decode the file, or transmit the file toanother client 1502. It is to be appreciated, that a client 1502 canalso transfer uncompressed file to a server 1504 and server 1504 cancompress the file in accordance with the disclosed subject matter.Likewise, server 1504 can encode video information and transmit theinformation via communication framework 1506 to one or more clients1502.

The illustrated aspects of the disclosure may also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

Moreover, it is to be appreciated that various components described inthis description can include electrical circuit(s) that can includecomponents and circuitry elements of suitable value in order toimplement the embodiments of the subject innovation(s). Furthermore, itcan be appreciated that many of the various components can beimplemented on one or more integrated circuit (IC) chips. For example,in one embodiment, a set of components can be implemented in a single ICchip. In other embodiments, one or more of respective components arefabricated or implemented on separate IC chips.

What has been described above includes examples of the embodiments ofthe present invention. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the claimed subject matter, but it is to be appreciated thatmany further combinations and permutations of the subject innovation arepossible. Accordingly, the claimed subject matter is intended to embraceall such alterations, modifications, and variations that fall within thespirit and scope of the appended claims. Moreover, the above descriptionof illustrated embodiments of the subject disclosure, including what isdescribed in the Abstract, is not intended to be exhaustive or to limitthe disclosed embodiments to the precise forms disclosed. While specificembodiments and examples are described in this disclosure forillustrative purposes, various modifications are possible that areconsidered within the scope of such embodiments and examples, as thoseskilled in the relevant art can recognize.

In particular and in regard to the various functions performed by theabove described components, devices, circuits, systems and the like, theterms used to describe such components are intended to correspond,unless otherwise indicated, to any component which performs thespecified function of the described component (e.g., a functionalequivalent), even though not structurally equivalent to the disclosedstructure, which performs the function in the disclosure illustratedexemplary aspects of the claimed subject matter. In this regard, it willalso be recognized that the innovation includes a system as well as acomputer-readable storage medium having computer-executable instructionsfor performing the acts and/or events of the various methods of theclaimed subject matter.

The aforementioned systems/circuits/modules have been described withrespect to interaction between several components/blocks. It can beappreciated that such systems/circuits and components/blocks can includethose components or specified sub-components, some of the specifiedcomponents or sub-components, and/or additional components, andaccording to various permutations and combinations of the foregoing.Sub-components can also be implemented as components communicativelycoupled to other components rather than included within parentcomponents (hierarchical). Additionally, it should be noted that one ormore components may be combined into a single component providingaggregate functionality or divided into several separate sub-components,and any one or more middle layers, such as a management layer, may beprovided to communicatively couple to such sub-components in order toprovide integrated functionality. Any components described in thisdisclosure may also interact with one or more other components notspecifically described in this disclosure but known by those of skill inthe art.

In addition, while a particular feature of the subject innovation mayhave been disclosed with respect to only one of several implementations,such feature may be combined with one or more other features of theother implementations as may be desired and advantageous for any givenor particular application. Furthermore, to the extent that the terms“includes,” “including,” “has,” “contains,” variants thereof, and othersimilar words are used in either the detailed description or the claims,these terms are intended to be inclusive in a manner similar to the term“comprising” as an open transition word without precluding anyadditional or other elements.

As used in this application, the terms “component,” “module,” “system,”or the like are generally intended to refer to a computer-relatedentity, either hardware (e.g., a circuit), a combination of hardware andsoftware, software, or an entity related to an operational machine withone or more specific functionalities. For example, a component may be,but is not limited to being, a process running on a processor (e.g.,digital signal processor), a processor, an object, an executable, athread of execution, a program, and/or a computer. By way ofillustration, both an application running on a controller and thecontroller can be a component. One or more components may reside withina process and/or thread of execution and a component may be localized onone computer and/or distributed between two or more computers. Further,a “device” can come in the form of specially designed hardware;generalized hardware made specialized by the execution of softwarethereon that enables the hardware to perform specific function; softwarestored on a computer readable storage medium; software transmitted on acomputer readable transmission medium; or a combination thereof.

Moreover, the words “example” or “exemplary” are used in this disclosureto mean serving as an example, instance, or illustration. Any aspect ordesign described in this disclosure as “exemplary” is not necessarily tobe construed as preferred or advantageous over other aspects or designs.Rather, use of the words “example” or “exemplary” is intended to presentconcepts in a concrete fashion. As used in this application, the term“or” is intended to mean an inclusive “or” rather than an exclusive“or”. That is, unless specified otherwise, or clear from context, “Xemploys A or B” is intended to mean any of the natural inclusivepermutations. That is, if X employs A; X employs B; or X employs both Aand B, then “X employs A or B” is satisfied under any of the foregoinginstances. In addition, the articles “a” and “an” as used in thisapplication and the appended claims should generally be construed tomean “one or more” unless specified otherwise or clear from context tobe directed to a singular form.

Computing devices typically include a variety of media, which caninclude computer-readable storage media and/or communications media, inwhich these two terms are used in this description differently from oneanother as follows. Computer-readable storage media can be any availablestorage media that can be accessed by the computer, is typically of anon-transitory nature, and can include both volatile and nonvolatilemedia, removable and non-removable media. By way of example, and notlimitation, computer-readable storage media can be implemented inconnection with any method or technology for storage of information suchas computer-readable instructions, program modules, structured data, orunstructured data. Computer-readable storage media can include, but arenot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

On the other hand, communications media typically embodycomputer-readable instructions, data structures, program modules orother structured or unstructured data in a data signal that can betransitory such as a modulated data signal, e.g., a carrier wave orother transport mechanism, and includes any information delivery ortransport media. The term “modulated data signal” or signals refers to asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in one or more signals. By way ofexample, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

In view of the exemplary systems described above, methodologies that maybe implemented in accordance with the described subject matter will bebetter appreciated with reference to the flowcharts of the variousfigures. For simplicity of explanation, the methodologies are depictedand described as a series of acts. However, acts in accordance with thisdisclosure can occur in various orders and/or concurrently, and withother acts not presented and described in this disclosure. Furthermore,not all illustrated acts may be required to implement the methodologiesin accordance with certain aspects of this disclosure. In addition,those skilled in the art will understand and appreciate that themethodologies could alternatively be represented as a series ofinterrelated states via a state diagram or events. Additionally, itshould be appreciated that the methodologies disclosed in thisdisclosure are capable of being stored on an article of manufacture tofacilitate transporting and transferring such methodologies to computingdevices. The term article of manufacture, as used in this disclosure, isintended to encompass a computer program accessible from anycomputer-readable device or storage media.

What is claimed is:
 1. A system, comprising: a processor configured toexecute computer executable components stored in a memory: an interfacecomponent configured to generate an interface that facilitates trackingcourse of care of a patient, wherein the interface comprises a pluralityof input compartments defined by a first axis comprising columnscorresponding to sequential points in time over the course of the careand a second axis comprising rows respectively corresponding to patientcare events or patient conditions associated with the course of thecare; a reception component configured to receive input regarding apatient care event or patient condition that occurred over the course ofcare; a logging component configured to fill one or more inputcompartments respectively corresponding to a point or period of timeassociated with occurrence of the patient care event or patientcondition; a tracking component configured to employ at least onealgorithm and at least one information source that defines relationshipsbetween patient conditions, patient care events, and a course of patientcare to infer issues associated with a condition of the patient; aninference component configured to: infer when the interface componentshould add one or more additional patient care events or patientconditions to the interface based on relationships between patient careevents and/or patient care conditions, a course of patient care, and acurrent point in the course of the patient care, wherein the inferenceis probabilistic; identify a specific context or action based on theinference; and construct one or more new events or actions; and apatient tracking tool configured to add one or more data fields based onthe one or more new events or actions.
 2. The system of claim 1, furthercomprising a presentation component configured to display the interface.3. The system of claim 1, wherein the reception component is configuredto receive the input in real time over the course of care.
 4. The systemof claim 1, further comprising a time component configured to trackprogression of time over the course of care, wherein the loggingcomponent is configured to determine the point or period of timeassociated with the occurrence of the patient care event or patientcondition based in part on a time of receipt of the input.
 5. The systemof claim 1, further comprising a time component configured to trackprogression of time over the course of care, wherein the input regardingthe patient care event or patient condition identifies a time of onsetof the patient care event or patient condition, and wherein the loggingcomponent is configured to automatically fill input compartments of arow corresponding to the patient care event or patient condition overthe course of care until new input is received that identifies a changein the patient care event or patient condition.
 6. The system of claim1, wherein the input relates to at least one of: a time of onset of thepatient care event or patient condition, a duration of time elapsedsince onset of the patient care event or patient condition, or a time ofchange in the patient care event or patient condition.
 7. The system ofclaim 1, wherein the input relates to a characteristic of the patientcare event or patient condition.
 8. The system of claim 1, wherein thelogging component is configured to fill the one or more inputcompartments with data that represents at least one of the occurrence ofthe patient care event or patient condition, or a characteristic of thepatient care event or patient condition, and wherein the data comprisesat least one of a color, a pattern, a symbol or text.
 9. The system ofclaim 1, wherein at least one of the input compartments includes a dropdown menu with input options that facilitate selection of one of theoptions for the input.
 10. The system of claim 1, wherein the receptioncomponent is configured to receive the input from a user via an inputdevice.
 11. The system of claim 1, wherein the reception component isconfigured to receive the input from a medical device.
 12. The system ofclaim 1, wherein the patient care events or patient conditionsrespectively associated with the rows are predefined.
 13. The system ofclaim 1, wherein the interface component is configured to receive userinput defining a patient care event or patient condition associated withone or more of the rows.
 14. The system of claim 1, further comprising atime component configured to track progression of time over the courseof care, wherein the interface component is configured to add additionalcolumns corresponding to current points in time as the course of carecontinues.
 15. The system of claim 1, further comprising a timecomponent configured to track progression of time over the course ofcare, wherein the interface component is configured to add one or moreadditional rows corresponding to a new patient event or new patientcondition relevant to the course of care as the course of carecontinues.
 16. The system of claim 1, wherein the inference component isconfigured to employ one or more classifiers to: determine a confidencethat certain input belongs to a certain class: and infer an action thata user desires to be automatically performed based on theclassification.
 17. A method comprising: using a processor to executethe following computer executable instructions stored in a memory toperform the following acts: generating an interface that facilitatestracking course of care of a patient, wherein the interface comprises aplurality of input compartments defined by a first axis comprisingcolumns corresponding to sequential points in time over the course ofthe care and a second axis comprising rows respectively corresponding topatient care events or patient conditions associated with the course ofthe care; receiving input regarding a patient care event or patientcondition that occurred over the course of the care; filling one or moreinput compartments respectively corresponding to a point or period oftime associated with occurrence of the patient care event or patientcondition, in response to reception of the input; employing at least onealgorithm and at least one information source that defines relationshipsbetween patient conditions, patient care events, and a course of patientcare to infer issues associated with a condition of the patient;inferring when the interface should display one or more additionalpatient care events or patient conditions within the interface based onrelationships between patient care events and/or patient careconditions, a course of patient care, and a current point in the courseof the patient care, wherein the inference is probabilistic; identifyinga specific context or action based on the inference; constructing one ormore new events or actions; and adding one or more data fields based onthe one or more new events and actions.
 18. The method of claim 17,further comprising displaying the interface at a device.
 19. The methodof claim 17, further comprising: tracking progression of time over thecourse of care; and determining the point or period of time associatedwith the occurrence of the patient care event or patient condition basedin part on a time of receipt of the input.
 20. The method of claim 17,further comprising: tracking progression of time over the course ofcare, wherein the input regarding the patient care event or patientcondition identifies a time of onset of the patient care event orpatient condition; and automatically filling input compartments of a rowcorresponding to the patient care event or patient condition over thecourse of care until new input is received that identifies a change inthe patient care event or patient condition.
 21. A non-transitorycomputer-readable medium comprising computer-readable instructions that,in response to execution, cause a computing system to performoperations, comprising: generating an interface that facilitatestracking a course of care of a patient, wherein the interface comprisesa plurality of input compartments defined by a first axis comprisingcolumns corresponding to sequential points in time over the course ofthe care and a second axis comprising rows respectively corresponding topatient care events or patient conditions associated with the course ofthe care; filling one or more input compartments respectivelycorresponding to a point or period of time associated with occurrence ofa patient care event or a patient condition based on input regarding theoccurrence of the patient care event or the patient condition;displaying the interface via a display screen of a device; employing atleast one algorithm and at least one information source that definesrelationships between patient conditions, patient care events, and acourse of patient care to infer issues associated with a condition ofthe patient; inferring when the interface should display one or moreadditional patient care events or patient conditions within theinterface based on relationships between patient care events and/orpatient care conditions, a course of patient care, and a current pointin the course of the patient care, wherein the inference isprobabilistic; identifying a specific context or action based on theinference; constructing one or more new events or actions; and addingone of more new data fields based on the one or more new events oractions.